Skip to content

Conversation

@tjuyuxinzhang
Copy link

Updates

  • Affected products
  • References

Comments
The advisory currently implies that all versions < 7.7.0 are affected, which incorrectly includes 6.6.6, a version that contains the backported fix. Adding an explicit branch fix range resolves the inaccuracy and avoids misreporting in vulnerability scanners.

The vulnerability was also backported to the maintained 6.6.x branch, and was fixed in version 6.6.6, via the following Apache commit:

add003f217806afb4e1604f697cdb0a5a7115895

Source:
apache/lucene-solr@add003f

Therefore, the actual affected version ranges should be expressed as:

6.6.0 – 6.6.5 (fixed in 6.6.6)

All versions < 7.7.0 on the main development line (fixed in 7.7.0)

This means 6.6.6 should not be listed as affected, but it is currently included under the < 7.7.0 range.

Updating the affected version definitions improves accuracy and prevents false positives in automated security scanners.

@github-actions github-actions bot changed the base branch from main to tjuyuxinzhang/advisory-improvement-6398 November 8, 2025 07:53
@advisory-database advisory-database bot merged commit c13cc77 into tjuyuxinzhang/advisory-improvement-6398 Nov 10, 2025
4 checks passed
@advisory-database
Copy link
Contributor

Hi @tjuyuxinzhang! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

@advisory-database advisory-database bot deleted the tjuyuxinzhang-GHSA-j346-h5wc-rw2m branch November 10, 2025 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants